asus-wmi: Restrict debugfs interface when the kernel is locked down
authorMatthew Garrett <matthew.garrett@nebula.com>
Wed, 5 Apr 2017 16:40:30 +0000 (17:40 +0100)
committerBen Hutchings <ben@decadent.org.uk>
Mon, 19 Jun 2017 23:25:45 +0000 (00:25 +0100)
commit19c316407ae4e841a7e1cf46afb04fb259e35a55
tree0d2047bdd7eead103eef25004fd673b910ab80f3
parent391133120820746d3148806414aa3521dd9326de
asus-wmi: Restrict debugfs interface when the kernel is locked down

We have no way of validating what all of the Asus WMI methods do on a given
machine - and there's a risk that some will allow hardware state to be
manipulated in such a way that arbitrary code can be executed in the
kernel, circumventing module loading restrictions.  Prevent that if the
kernel is locked down.

Signed-off-by: Matthew Garrett <matthew.garrett@nebula.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Gbp-Pq: Topic features/all/lockdown
Gbp-Pq: Name 0053-asus-wmi-Restrict-debugfs-interface-when-the-kernel-.patch
drivers/platform/x86/asus-wmi.c